** Element Version (Client-side) **
1) Add the "XLSX | CSV To JSON PRO" element to your page.

2) Configure the element properties:

- file url: Enter the URL(s) of your CSV or XLSX file(s), separated by commas if multiple.

- max rows: Set a maximum number of rows to process (optional).

- columns to include: List the columns to include, separated by commas (optional).

- default value: Specify a value for empty cells (optional).

- filter condition: Enter condition to filter rows (optional).

- analysis types: Specify 'sum', 'average', or both, separated by commas (optional).


3) Use a button or workflow to trigger the "Refresh data of element" action on the XLSX | CSV To JSON PRO.

4) Access the processed data through the element's exposed states:

- json output: Contains the processed data as a JSON string.

- file size kb: Total size of processed files in KB.

- column names: List of column names in the processed data.

- total rows: Number of rows in the processed data.

- analysis results: Results of requested data analysis.


** Action Version (Server-side) **

1) Add the "XLSX | CSV To JSON PRO" action to your workflow.

2) Configure the action parameters:

- file url: Enter the URL(s) of your CSV or XLSX file(s), separated by commas if multiple.

- max rows: Set a maximum number of rows to process (optional).

- columns to include: List the columns to include, separated by commas (optional).

- default value: Specify a value for empty cells (optional).

- filter condition: Enter condition to filter rows (optional).

- analysis types: Specify 'sum', 'average', or both, separated by commas (optional).


3) Use the action's return values in subsequent steps of your workflow:

- json output: Contains the processed data as a JSON string.

- file size kb: Total size of processed files in KB.

- column names: List of column names in the processed data.

- total rows: Number of rows in the processed data.

- analysis results: Results of requested data analysis.


** Notes **

- Ensure your file URLs are accessible to the plugin.

- Large files may take longer to process, especially in the client-side version.

- The server-side action may be more suitable for processing larger files or when client-side resources are limited.

- Complex filter conditions or analysis of large datasets may impact performance.